Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

To handle error cleanly #17

Merged
merged 1 commit into from Nov 21, 2012
Merged

To handle error cleanly #17

merged 1 commit into from Nov 21, 2012

Conversation

Raynos
Copy link
Contributor

@Raynos Raynos commented Nov 21, 2012

I need to be able to destroy that stream

@Raynos
To handle error cleanly
546e8d8 
I need to be able to destroy that stream
@dominictarr dominictarr merged commit 546e8d8 into dominictarr:master Nov 21, 2012
@dominictarr
Copy link
Owner

merged to mux-demux@3.3.6

@dominictarr
Copy link
Owner

looking at this in the morning, realized that this is never a problem with classic streams,
because pipe checks whether the destination is writable before it calls write(data)

@Raynos
Copy link
Contributor Author

Raynos commented Nov 21, 2012

@dominictarr yeah that's why I filed a bug on readable-stream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@Raynos @dominictarr